Skip to content

Rename param files#1647

Draft
amilcarlucas wants to merge 9 commits into
masterfrom
rename_param_files
Draft

Rename param files#1647
amilcarlucas wants to merge 9 commits into
masterfrom
rename_param_files

Conversation

@amilcarlucas
Copy link
Copy Markdown
Collaborator

Description

Re-organize the configuration steps

  • add new ones to cover new functionality
  • separate existing ones into sub-steps
  • delete steps that produced little benefits or whose parameters got moved to other steps

Parameters also moved between steps

Checklist

  • Run pre-commit checks locally
  • Verified by a human programmer
  • All commits are signed off (use git commit --signoff)
  • Code follows our coding standards
  • Documentation updated if needed
  • No breaking changes or properly documented

Testing

Describe how you tested these changes:

  • Unit tests pass
  • Integration tests pass
  • Manual testing performed
  • Tested on flight controller hardware

…rsion 1 before filesystem init

- Introduce backend_filesystem_migration.py
- Adds format-version migration support for legacy vehicle projects
- Handles parameter extraction from old files into new step files
- Creates new fixed-content parameter files
- Removes obsolete legacy files
- Updates vehicle_components.json format version after migration
- Integrate migration into startup in __main__.py
- Run migrate_vehicle_project_if_needed(state.args.vehicle_dir) before LocalFilesystem creation
- Ensures renamed/split parameter files exist before local filesystem initialization

Update step metadata in JSON:
- configuration_steps_ArduCopter.json
- Add new step entries for migrated files (04_imu_temperature_calibration_finish.param, 07_remote_controller_controller.param, 10_battery_monitor.param, 17_safety_setup.param, 14_logging.param, 26_pid_notch_filter_logging.param, 45_autotune_finish.param, 49_windspeed_estimation_finish.param, plus others)
- Adjust derived/forced/delete parameter logic for new step placement

Testing / validation notes:
- backend_filesystem_migration.py compiles successfully
- Updated JSON files parse correctly

This commit makes legacy vehicle project upgrades automatic and consistent with the new parameter file layout and step metadata.
Copilot AI review requested due to automatic review settings May 26, 2026 15:27
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot wasn't able to review this pull request because it exceeds the maximum number of files (300). Try reducing the number of changed files and requesting a review from Copilot again.

@amilcarlucas amilcarlucas marked this pull request as draft May 26, 2026 15:29
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 26, 2026

☂️ Code Coverage

current status: ✅

Overall Coverage

Statements Covered Coverage Threshold Status
12810 12039 94% 89% 🟢

New Files

No new covered files...

Modified Files

No covered modified files...

updated for commit: 25b3ead by action🐍

@github-actions
Copy link
Copy Markdown
Contributor

Test Results

     4 files       4 suites   41m 45s ⏱️
 3 797 tests  3 794 ✅  3 💤 0 ❌
14 980 runs  14 951 ✅ 29 💤 0 ❌

Results for commit 25b3ead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants